Tree

There is a problem

1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1499

reference: 572-tree-1
name: 1499
tree-preservation-order: undefined
572-tpo-1
uprn
address-text
point: POINT (-0.971639 50.866783)
geometry: MULTIPOLYGON (((-0.971568 50.866776,-0.971571 50.866790,-0.971581 50.866802,-0.971596 50.866812,-0.971616 50.866819,-0.971638 50.866821,-0.971660 50.866819,-0.971680 50.866813,-0.971696 50.866803,-0.971706 50.866791,-0.971710 50.866777,-0.971707 50.866763,-0.971697 50.866750,-0.971681 50.866740,-0.971662 50.866734,-0.971640 50.866731,-0.971618 50.866733,-0.971598 50.866740,-0.971582 50.866749,-0.971571 50.866762,-0.971568 50.866776)))
notes
felled-date
entry-date: 2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

Fix the errors indicated
Use the check service to make sure the data meets the standard
Publish the updated data on the endpoint URL